Apparatus and method for managing remote user interface and system for the same

ABSTRACT

A system for managing a Remote User Interface (RUI) includes a Remote User Interface Server (RUIS) for sending an update message indicating that an RUI list including at least one RUI has been updated, and transmitting updated RUI list information upon receiving a request for updated RUI list information; and a Remote User Interface Client (RUIC) for sending a request for updated RUI list information to the RUIS upon recognizing from the update message received from the RUIS that an RUI list has been updated, receiving the updated RUI list information from the RUIS in response to the request, and updating existing RUI list information based on the updated RUI list information.

PRIORITY

This application claims priority under 35 U.S.C. §119(a) to an application filed in the Korean Intellectual Property Office on Jul. 13, 2010 and assigned Serial No. 10-2010-0067608, the entire disclosure of which is incorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to a Remote User Interface (RUI), and more particularly, to an apparatus and method for managing an RUI and a system for the same.

2. Description of the Related Art

Several industry standards organizations such as Digital Living Network Alliance (DLNA), Home Audio-Video Interoperability (HAVi), and Universal Plug and Play (UPnP) have conducted studies to improve home network technology, including Remote User Interface (RUI) technology, which may be used in a home network to allow one device to control the functions of other devices. Briefly, the RUI technology, based on client-server architecture, allows an RUI Client (RUIC) to fetch a UI from an RUI Server (RUIS) and helps a user control the RUIS utilizing the UI on the RUIC.

Consumer Electronics Association (CEA)-2014 is a standard for RUI, which defines a protocol and a framework for RUIs in a Universal Plug and Play (UPnP) network and the Internet. In accordance with CEA-2014, an UPnP device (RUIS) provides a user interface in a web page in the form of Consumer Electronics-Hypertext Markup Language (CE-HTML), and a user may control an application of the UPnP device remotely on the web page. CE-HTML, a special version of HTML, is based on Extensible HTML (XHTML).

FIG. 1 illustrates a configuration of a general UPnP network. The UPnP network includes an RUIC 110, an RUIS 130, and a UI Control Point (UICP) 150. The RUIC 110 renders and controls an RUI(s) delivered from the RUIS 130. The RUIS 130 provides at least one RUI.

The UICP 150 discovers the RUIC 110 and the RUIS 130, and establishes a connection between the RUIC 110 and the RUIS 130. Although the RUIC 110 and the UICP 150 are illustrated as separate elements in the drawing, the RUIC 110 may directly discover the RUIS 130 when the UICP 150 is embedded in the RUIC 110.

If the RUIC 110 does not include the UICP 150, and a separate UICP intends to send an RUI of the RUIS 130 to the RUIC 110, even the RUIC 110 may be discovered by the UICP through discovery.

To use an RUI in the home network, discovery for the RUIC 110 and the RUIS 130 is performed. After performing the discovery, the RUIC 110 acquires an RUI page depending on a Uniform Resource Locator (URL) with the RUI page, which is included in a device description. Because the RUI page is composed to make it possible to control an application of the RUIS 130, the RUIC 110 may control the application of the RUIS 130 using the RUI page.

FIG. 2 illustrates a signaling operation for communication between an RUIS and an RUIC according to the prior art.

In order to use an RUI stored in the RUIS 130, the RUIC 110 needs to receive a RUI list and a discovery procedure between the RUIC 110 and the RUIS 130 is required. Therefore, in step 201, devices (e.g., RUIC 110 and RUIS 130) discover each other and receive an associated device description.

In step 203, the RUIC 110 sends a request for an RUI list to the RUIS 130 depending on a URL with an RUI page, which is included in the device description. In step 205, the RUIS 130 sends an RUI list to the RUIC 110 in response to the RUI list request.

The RUIC 110 provides the RUI list received from the RUIS 130 in step 207, and sends a request for an RUI page to the RUIS 130 in step 209. In step 211, the RUIS 130 provides or transmits the RUI page to the RUIC 110 in response to the RUI page request.

Currently, however, even though an RUI list in an RUIS has been updated after an RUIC received an RUI page from the RUIS, the RUIC is incapable of receiving an updated RUI list.

SUMMARY OF THE INVENTION

Accordingly, an aspect of the present invention is to address at least the aforementioned limitations and problems in the prior art and to provide at least the advantages described below. Accordingly, an aspect of the present invention provides an apparatus and method for notifying an RUIC of an update, if any, of an RUI list in an RUIS to update the RUI list, and a system for the same.

Another aspect the present invention provides an apparatus and method for allowing an RUIC to use an updated RUI list, and a system for the same.

In accordance with one aspect of the present invention, there is provided a system for managing a Remote User Interface (RUI). The system includes a Remote User Interface Server (RUIS) for sending an update message indicating that an RUI list including at least one RUI has been updated, and transmitting updated RUI list information upon receiving a request for updated RUI list information; and a Remote User Interface Client (RUIC) for sending a request for updated RUI list information to the RUIS upon recognizing from the update message received from the RUIS that an RUI list has been updated, receiving the updated RUI list information from the RUIS in response to the request, and updating existing RUI list information based on the updated RUI list information.

In accordance with another aspect of the present invention, there is provided an apparatus for managing a Remote User Interface (RUI) in a Remote User Interface Server (RUIS). The apparatus includes a manager for managing at least one RUI to be provided to a Remote User Interface Client (RUIC), and determining whether an RUI list including the at least one RUI has been updated; a generator for generating an update message if the RUI list has been updated; and a transceiver for sending the generated update message to the RUIC, receiving a request for updated RUI list information in response to the update message, and transmitting the updated RUI list information to the RUIC in response to the received request for updated RUI list information.

In accordance with another aspect of the present invention, there is provided a method for managing a Remote User Interface (RUI) in a Remote User Interface Server (RUIS). The method includes determining whether an RUI list including at least one RUI has been updated; if the RUI list has been updated, generating an update message and sending the update message to a Remote User Interface Client (RUIC); and upon receiving a request for updated RUI list information in response to the update message, transmitting updated RUI list information to the RUIC in response to the request for updated RUI list information.

In accordance with another aspect of the present invention, there is provided an apparatus for managing a Remote User Interface (RUI) in a Remote User Interface Client (RUIC). The apparatus includes a parser for parsing an update message received from a Remote User Interface Server (RUIS); a manager for managing at least one RUI provided from the RUIS, generating a request message for requesting the RUIS to provide updated RUI list information upon recognizing from the received update message that an RUI list has been updated, and updating existing RUI list information based on the updated RUI list information upon receiving the updated RUI list information in response to the request message; and a transceiver for receiving the update message, delivering the received update message to the parser, sending the request message generated by the manager to the RUIS, and delivering the updated RUI list information to the manager in response to the request message.

In accordance with another aspect of the present invention, there is provided a method for managing a Remote User Interface (RUI) in a Remote User Interface Client (RUIC). The method includes sending a request for updated RUI list information to a Remote User Interface Server (RUTS) in response to an update message received from the RUIS; receiving the updated RUI list information from the RUIS in response to the request; and updating existing RUI list information based on the updated RUI list information.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features and advantages of certain embodiments of the present invention will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:

FIG. 1 is a diagram illustrating a configuration of a general UPnP network;

FIG. 2 is a signaling diagram illustrating a signaling operation for communication between an RUIS and an RUIC according to the prior art;

FIG. 3 is a block diagram illustrating a structure of an RUIC according to an embodiment of the present invention;

FIG. 4 is a block diagram illustrating a structure of an RUIS according to an embodiment of the present invention;

FIG. 5 is a diagram illustrating a device description according to an embodiment of the present invention;

FIG. 6 is a flowchart illustrating an RUI list management operation in an RUIC according to an embodiment of the present invention;

FIG. 7 is a flowchart illustrating an RUI list management operation in an RUIS according to an embodiment of the present invention; and

FIG. 8 is a signaling diagram illustrating a signaling operation for communication between an RUIC and an RUIS according to an embodiment of the present invention.

Throughout the drawings, the same drawing reference numerals will be understood to refer to the same elements, features and structures.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE PRESENT INVENTION

Various embodiments of the present invention will now be described in detail with reference to the accompanying drawings. In the following description, specific details such as detailed configurations and components are merely provided to assist the overall understanding of the embodiments of the present invention. Therefore, various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. In addition, descriptions of well-known functions and constructions are omitted for clarity and conciseness.

An RUI service, to which the present invention is directed, is a service in which an RUIS provides an RUI(s), and an RUIC may control a device in a remote place on the provided RUI. The present invention updates an RUI list in an RUIC each time an RUI list in an RUIS is updated in the RUI service.

FIG. 3 illustrates a structure of an RUIC according to an embodiment of the present invention. The RUIC 110 includes a transceiver 310, a parser 330, a manager 350, and a display 370.

The transceiver 310 receives an update message from the RUIS 130, sends a request message for requesting to provide updated RUI list information in response to the update message, and receives the updated RUI list information in response to the request message.

The parser 330 parses the update message, and determines in which method it will receive the updated RUI list depending on the parsing results. The parser 330 parses information about a location of an RUI list, where the RUIC 110 can receive the RUI list, for example, determines if a URL has been changed. If the URL has not been changed, the parser 330 determines to receive the RUI list depending on a value of a uiListURL Element written in a device description. On the other hand, if the URL has been changed, the parser 330 renders the updated RUI list information included in the update message, and then determines to receive an RUI list depending on a changed value of the uiListURL Element, which is the URL. The parser 330 may determine whether a URL has been changed, by checking if URL information is included in the update message.

The device description will be described in detail below with reference to FIG. 5. The manager 350, a component for storing and managing RUI list information provided from the RUIS 130, generates a request message for requesting to provide updated RUI list information depending on the parsing results by the parser 330, and updates RUI list information based on the RUI list information received from the RUIS 130.

The display 370 displays the updated RUI list information. The display 370 may display the updated-RUI list information right after the update was performed in the manager 350, or may display the updated-RUI list information upon the request of the user.

FIG. 4 illustrates a structure of an RUIS according to an embodiment of the present invention. The RUIS 130 includes a transceiver 410, a manager 430, and a generator 450.

The transceiver 410 sends an update message to the RUIC 110, receives a request message for requesting to provide updated RUI list information from the RUIC 110, and sends updated RUI list information in response to the request message.

The manager 430 stores and manages at least one RUI to be provided to the RUIC 110, and determines if an RUI list including the at least one RUI has been updated.

The generator 450 generates an update message according to the determination results, and generates updated RUI list information in response to the request message received from the RUIC 110. Otherwise, the generator 450 may generate updated RUI list information in advance before receiving the request message from the RUIC 110.

The update message mentioned in the present invention, which is a message to be sent from an RUIS to an RUIC, includes at least one of header information, delivery target information, multicast address information, URL change/non-change information, changed URL information, and unchanged URL information. If necessary, the update message may further include additional information in addition to the above six kinds of information.

FIG. 5 illustrates a device description according to an embodiment of the present invention. The device description, an information element provided from the RUIS 130 to the RUIC 110 in step 201 of FIG. 2, is used to indicate whether the RUIS 130 may provide an updated RUI list to the RUIC 110 depending on a ‘renewable’ attribute included in the existing uiListURL element.

Referring to FIG. 5, if a ‘renewable’ attribute 510 is set to ‘yes’, the RUIS 130 may provide an updated RUI list to the RUIC 110. However, if the ‘renewable’ attribute 510 is set to ‘no’, the RUIS 130 may not provide an updated RUI list to the RUIC 110. That is, the ‘renewable’ attribute 510 makes it possible for the RUIC 110 to determine if it can receive an updated RUI list from the RUIS 130. This ‘renewable’ attribute is not limited to the ‘renewable’ attribute 510 illustrated in FIG. 5 in terms of its location, and may exist in any location in the device description.

FIG. 6 illustrates an RUI list management operation in an RUIC according to an embodiment of the present invention. In step 601, an RUIC 110 receives an update message from an RUIS 130. In step 603, the RUIC 110 parses the update message, and determines in which method it will receive an updated RUI list depending on the parsing results. Here, the RUIC 110 parses information about a location of an RUI list, where the RUIC 110 can receive the RUI list, for example, determines if a URL has been changed. The RUIC 110 may determine if a URL has been changed, by checking if a URL is included in the update message. That is, if a URL is included in the update message, the RUIC 110 may determine that the URL has been changed. If no URL is included in the update message, the RUIC 110 may determine that the URL has not been changed.

If the RUIC 110 parses the update message, and determines in step 603 that a URL of the RUI list has been changed, the RUIC 110 extracts changed location information (i.e., changed URL information) included in the update message in step 605, and requests to provide updated RUI list information using a changed value of the uiListURL Element, which is the URL, in step 607.

The RUIC 110 receives updated RUI list information from the RUIS 130 in response to the request in step 609, and updates its RUI list information based on the updated RUI list information in step 611.

However, if the RUIC 110 parses the update message, and determines in step 603 that the URL of the RUI list has not been changed, the RUIC 110 proceeds to step 607, skipping step 605 and may request the updated RUI list information using the existing unchanged URL.

FIG. 7 illustrates an RUI list management operation in an RUIS according to an embodiment of the present invention. In step 701, an RUIS 130 determines if an RUI list including at least one RUI has been updated. If it is determined in step 130 that the RUI list has been updated, the RUIS 130 generates an update message and sends it to an RUIC 110 in step 703.

The RUIS 130 receives a request for updated RUI list information from the RUIC 110 in response to the update message in step 705, and transmits the updated RUI list information in response to the request from the RUIC 110 in step 707.

FIG. 8 illustrates a signaling operation for communication between an RUIC and an RUIS according to an embodiment of the present invention. In step 801, an RUIS 130 determines if its RUI list has been updated. If the RUI list has been updated, the RUIS 130 sends an update message to an RUIC 110 in step 803.

In step 805, the RUIC 110 determines if a URL of the RUI list has been changed by parsing the update message received from the RUIS 130. If it is determined in step 805 that the URL of the RUI list has been changed, the RUIC 110 extracts the changed location information (i.e., changed URL information) included in the update message in step 807, and requests the RUIS 130 to provide updated RUI list information using a changed value of the uiListURL Element, which is the URL, in step 809.

However, if it is determined in step 805 that the URL of the RUI list has not been changed, the RUIC 110 proceeds to step 809, skipping step 807.

In step 811, the RUIS 130 transmits the updated RUI list information to the RUIC 110 in response to the request in step 809. Upon receiving the updated RUI list information, the RUIC 110 updates its RUI list information based on the updated RUI list information in step 813.

As is apparent from the foregoing description, if an RUI list in an RUIS is updated, the present invention notifies an RUIC of the update to update its RUI list, making it possible for the RUIC to use the updated RUI list.

While the present invention has been shown and described with reference to certain embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present invention as defined by the appended claims and their equivalents. 

1. A system for managing a Remote User Interface (RUI), comprising: a Remote User Interface Server (RUIS) for sending an update message indicating that an RUI list including at least one RUI has been updated, and transmitting updated RUI list information upon receiving a request for updated RUI list information; and a Remote User Interface Client (RUIC) for sending a request for updated RUI list information to the RUIS upon recognizing from the update message received from the RUIS that an RUI list has been updated, receiving the updated RUI list information from the RUIS in response to the request, and updating existing RUI list information based on the updated RUI list information.
 2. The system of claim 1, wherein the update message includes at least one of header information, delivery target information, multicast address information, Uniform Resource Locator (URL) change/non-change information, changed URL information, and unchanged URL information.
 3. The system of claim 1, wherein the RUIC requests the updated RUI list information based on at least one of location information included in the update message received from the RUIS and predetermined location information.
 4. The system of claim 3, wherein the RUIC determines whether the location information is included in the update message, if the location information is included in the update message, the RUIC requests the updated RUI list information based on the location information included in the update message, and if the location information is not included in the update message, the RUIC requests updated RUI list information based on the predetermined location information.
 5. The system of claim 3, wherein the location information includes URL information corresponding to a location where the updated RUI list information exists in the RUIS.
 6. The system of claim 5, wherein the RUIC, upon recognizing by parsing the update message that URL information has been changed, requests the updated RUI list information based on URL information in the update message, and upon recognizing by parsing the update message that URL information has not been changed, requests the updated RUI list information based on at least one of URL information in the update message and predetermined URL information.
 7. The system of claim 1, wherein if the RUIC is discovered by a discovery procedure of a neighboring device, the RUIS notifies whether an RUI list information update function is provided, using a device description being provided to the RUIC.
 8. The system of claim 6, wherein the RUIC determines whether an RUI list information update function is supportable by the RUIS, after recognizing the RUIS by a discovery procedure of a neighboring device, based on a renewable attribute written in a device description being provided from RUIS.
 9. An apparatus for managing a Remote User Interface (RUI) in a Remote User Interface Server (RUIS), comprising: a manager for managing at least one RUI to be provided to a Remote User Interface Client (RUIC), and determining whether an RUI list including the at least one RUI has been updated; a generator for generating an update message if the RUI list has been updated; and a transceiver for sending the generated update message to the RUIC, receiving a request for updated RUI list information in response to the update message, and transmitting the updated RUI list information to the RUIC in response to the received request for updated RUI list information.
 10. The apparatus of claim 9, wherein the update message includes at least one of header information, delivery target information, multicast address information, Uniform Resource Locator (URL) change/non-change information, changed URL information, and unchanged URL information.
 11. The apparatus of claim 9, wherein if the RUIC is discovered by a discovery procedure of a neighboring device, the generator generates a device description for notifying whether an RUI list information update function is provided and the transceiver provides the device description to the RUIC.
 12. A method for managing a Remote User Interface (RUI) in a Remote User Interface Server (RUIS), comprising: determining whether an RUI list including at least one RUI has been updated; generating an update message and sending the update message to a Remote User Interface Client (RUIC) if the RUI list has been updated; and transmitting updated RUI list information to the RUIC in response to a request for updated RUI list information upon receiving the request for updated RUI list information in response to the update message.
 13. The method of claim 12, wherein the update message includes at least one of header information, delivery target information, multicast address information, Uniform Resource Locator (URL) change/non-change information, changed URL information, and unchanged URL information.
 14. The method of claim 12, further comprising: generating a device description for notifying whether an RUI list information update function is provided if the RUIC is discovered by a discovery procedure of a neighboring device; and transmitting the device description to the RUIC.
 15. An apparatus for managing a Remote User Interface (RUI) in a Remote User Interface Client (RUIC), comprising: a parser for parsing an update message received from a Remote User Interface Server (RUIS); a manager for managing at least one RUI provided from the RUIS, generating a request message for requesting the RUIS to provide updated RUI list information upon recognizing from the received update message that an RUI list has been updated, and updating existing RUI list information based on the updated RUI list information upon receiving the updated RUI list information in response to the request message; and a transceiver for receiving the update message, delivering the received update message to the parser, sending the request message generated by the manager to the RUIS, and delivering the updated RUI list information to the manager in response to the request message.
 16. The apparatus of claim 15, wherein the update message includes at least one of header information, delivery target information, multicast address information, Uniform Resource Locator (URL) change/non-change information, changed URL information, and unchanged URL information.
 17. The apparatus of claim 15, wherein the transceiver sends the request message generated by the manager to the RUIS based on at least one of URL information included in the update message received from a RUIS and predetermined URL information.
 18. The apparatus of claim 17, wherein the parser determines whether URL information is included in the update message, and recognizes that the URL information has been changed if the URL information is included in the update message and recognizes that the URL information has not been changed if the URL information is not included in the update message.
 19. The apparatus of claim 18, wherein the transceiver, upon recognizing that the URL information has been changed, sends the request message based on the URL information included in the update message, and upon recognizing that the URL information has not been changed, sends the request message based on the predetermined URL information.
 20. The apparatus of claim 17, wherein the RUIC determines whether an RUI list information update function is supportable by the RUIS, after recognizing the RUIS by a discovery procedure of a neighboring device, based on a renewable attribute written in a device description being provided from RUIS.
 21. A method for managing a Remote User Interface (RUI) in a Remote User Interface Client (RUIC), comprising: sending a request for updated RUI list information to a Remote User Interface Server (RUIS) in response to an update message received from the RUIS; receiving the updated RUI list information from the RUIS in response to the request; and updating existing RUI list information based on the updated RUI list information.
 22. The method of claim 21, wherein the update message includes at least one of header information, delivery target information, multicast address information, Uniform Resource Locator (URL) change/non-change information, changed URL information, and unchanged URL information.
 23. The method of claim 21, wherein the request for updated RUI list information is sent based on at least one of URL information included in the update message and predetermined URL information.
 24. The method of claim 23, wherein sending a request for updated RUI list information comprises: determining whether URL information is included in the update message; sending the request for updated RUI list information if the URL information is included in the update message, based on the URL information included in the update message; and sending the request for updated RUI list information if the URL information is not included in the update message, based on the predetermined URL information. 